Insurance Database
Overview
My role: Architecture to deployed system, run and maintain.
Challenge: Provide timely information about insurance producers to management organisations through a convenient web portal.
Solution: Establish an extraction-transformation-loading (ETL) pipeline from the National Insurance Producer Registry (NIPR) to the information portal.
Technologies: Quarkus, Java 21, WordPress
Producers??
As it turns out, they are called insurance producers. Companies and individuals who are selling insurance. They are licensed by states to sell certain kinds of insurance products. Knowing which insurance producer has what license in which state is key information for organizations managing insurance producers.
Records and Alerts
The main national body that tracks insurance producers and their licenses is the NIPR. They provide full records about insurance producers showing every possible state and license they have or had in the past. They also provide daily incremental updates of any changes. The challenge is to manage the list of insurance producers, the management organizations are tracking, ensure that we have the full record and then keep it up to date through the daily alerts.
We Love XML and SOAP
The information we need to display to the management organizations is not presented entirely the way we could directly use it in the portal. Indeed, it is entirely in a very, very different format... The ETL pipeline maps existing data, newly downloaded full records, as well as daily alerts, ensures consistent, reliable updates. For full transparency, the system shows each version and changes detected on a timeline for administrators to verify that all mapping and changes are correct. For the end users, all this is transparent as they can use the modern, convenient web UI to access, search, and read the information.

